Does anyone know of a way to set the screen resolution during an OSD task sequence to the "recommended" setting for Windows 7? What I mean is if you go into the screen resolution control panel applet you will see one resolution in there with "(recommended)" next to it. It would be nice to programatically set that during OSD deployment versus using answer files.

As long as you have the video drivers injected correctly, and PnP vCard/Monitor (which they all are these days), Win7 (and WinXP for that matter) will automatically set the screen resolution to the native resolution of the monitor. This is typically 1280x1024, unless it's a widescreen then it's dependant on the size, probably 720p or 1080p.Scott Gill SCCM Consultant

Thanks Scott. If that is the case with my MDT 2010 + SCCM R2 SP2 environment then somewhere in the files/task sequence created by the "Create Microsoft Deployment Task Sequence" it is being set to 1024x768. Do you happen to know where I need to strip this out so it does it automagically?

What size monitors do you have? Some of the 17" and smaller older monitors are 1024x768 native.Scott Gill SCCM Consultant

It supports higher resolutions. After the OSD is complete I go into the screen resolution area and see the "recommended" which is higher than the 1024x768 that is set. I am now under the assumption the resolution is coded in the MDT files. I will look around.

I wouldn't think something like the resolution would have anything to do with MDT. Generally that information is in the sysprep.xml file on the system. Have you tried looking at the sysprep file inside of the WIM file?Scott Gill SCCM Consultant

I haven't tried looking in the WIM file yet. I will mount it and look at it. I have two sets of unattend.xml/customsettings.ini that I used in this deployment. One for reference machine deployment and image capture. The other for target machine deployment. I tried removing all mention of 1024x768 from the target deployment unattend.xml but it still deploys at 1024x768. Do I need to remove the 1024x768 from the reference machine unattend.xml? That sounds counter-intuitive.

you can force the resolution on the deployed sytem by editing the unattend.xml file in Windows SIM , and then saving that file, creating a package of that file and then using that unattend.xml file in the apply operating system image step within the task sequence. settings pass = "oobeSystem " component name = "Microsoft-Windows-Shell-Setup " <Display> <ColorDepth>16</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <RefreshRate>60</RefreshRate> <VerticalResolution>768</VerticalResolution> </Display> for example ^ don't forget to update the dp with the new version of your unattend.xml file after making any changes, you can verify the settings after deployment by reading the zticonfigure.log file if you can't figure this out i can post an unattend.xml file for you to do just that, let me know cheers niall My step by step SCCM Guides I'm on Twitter

i have been referencing an unattend.xml during my apply operating system image in the task sequence. the original version of the file had a reference to 1024x768. i removed that entry completely as i was under the impression if there is nothing in there then windows will automatically set the "recommended" setting. would it be better for me to choose the highest resolution possible for all of my machines and then windows will choose the next appropriate lower resolution when deploying to a machine that can't handle that resolution? i had read that is how it works somewhere on the interweb but am unsure if that is true.

Did you set these properties somewhere initially when capturing the image (or before)? I find it best not to specify such settings anywhere and Windows will just figure it out.Scott Gill SCCM Consultant

I didn't specify a resolution. I assume it was injected as part of MDT integration as MDT creates the unattend.xml?

What hardware models are you building for? I am currently deploying Windows XP SP3 using ConfigMgr R2 SP2 with MDT 2010 and the resolution is set correctly for all Dell hardware but not HP hardware. For HP hardware I have installed SetRefresh which automatically sets the optimal resolution when the user logs in for the first time and this works well :)Hope this helps.

Does anyone know of a way to set the screen resolution during an OSD task sequence to the "recommended" setting for Windows 7? What I mean is if you go into the screen resolution control panel applet you will see one resolution in there with "(recommended)" next to it. It would be nice to programatically set that during OSD deployment versus using answer files. I have not used this in SCCM but I don't see why it wouldn't work. I have had this script for a while and couldn't find the qres.exe commandline tool but I am sure you could easily find it in some dark corner of the internet. If it needed to be adjusted to meet some additional requirements I would be willing to give you some assistance.On Error Resume Next Const wbemFlagReturnImmediately = &h10Const wbemFlagForwardOnly = &h20 arrComputers = Array("localhost")For Each strComputer In arrComputers Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_DisplayConfiguration", "WQL", _ wbemFlagReturnImmediately + wbemFlagForwardOnly) If objItem.PelsWidth <= 800 then set oShell = CreateObject("WScript.Shell") oShell.run"qres.exe /x 1024 /y 768" end if If objItem.BitsPerPixel < 32 then set oShell = CreateObject("WScript.Shell") oShell.run"qres.exe /c:32" end ifnextMike Niccum

I had the same problem... check your unattended.xml file for a specific resolution setting and try removing it. If a specific resolution is defined in unattended.xml, a newly deployed machine will use that by default. If nothing is specified, it should use the native resolution of the monitor if your driver is appropriate.

Sorry to resurrect this. What if you have different sized monitors all over the school? Even some laptops are different resolutions.

Have you checked out the HP SetRefresh utility?

No I haven't. Have you? If so, would you know how to set it up? Would it work on non-HP computers as well?

matambanadzo, Did you find an answer to this? I'm coming across the same issue!!

Hi Alex, No, no-one has provided a solution for me. I ended up creating a task sequence for each different monitor size we have in the school. Then when it comes to imaging, we choose the task sequence that is the correct monitor size for the computer. In the task sequences we have an application that applies the correct resolution (http://www.naughter.com/qres.html) at the end of the sequence So the application command looks something like this ... resswitch.exe 1366 768 32 0 Instructions are included in the zip download from the site above.

You really shouldn't need to have seperate task sequences for each device. First make sure you do not have driver conflicts by injecting only the INF files for the monitor attached to the system (see http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/132/language/en-US/Default.aspx for details, you would use scenario 3). Also note that some monitors don't always detect properly in winPE, so you may have to choose the "Install all drivers from the profile" option. Once you have verified that the right INF file is being injected for the right device, (check ztidrivers.log and pnpenum.xml) and it's still not working, verify that the unattend.xml is not setting it for you. Use Windows System Image manager to edit the answer file to have the colordepth, refreshrate and resolution set to 1 (you can leave DPI blank). These setting are under 7 oobesystem\...shell setup\display. I have tried this under MDT2010 update 1 under a plethora of IBM thinkpads and Dells

No need to run a script to change the recommended resolution, the reason why this is happening is unattend.xml. 1024X768 is hard coded in MDT template unattend.xml. Display value needs to be deleted